This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Repository navigation
Expose public indexer and length properties on RefEnumerable<T> and ReadOnlyRefEnumerable<T> - #4047
Merged
10 commits merged intoJul 7, 2021
Conversation
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #4043
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently,
RefEnumerable<T>(and its read-only variant) do not expose an indexer or their length. This can make it difficult to implement certain APIs against them, such as a function to reverse their data.What is the new behavior?
This PR exposes public length and indexer properties (for both
intandSystem.Index) on bothRefEnumerable<T>andReadOnlyRefEnumerable<T>.public partial readonly ref struct RefEnumerable<T> { + public int Length { get; } + public ref T this[int index] { get; } + public ref T this[Index index] { get; } } public partial readonly ref struct ReadOnlyRefEnumerable<T> { + public int Length { get; } + public ref readonly T this[int index] { get; } + public ref readonly T this[Index index] { get; } }PR Checklist
Please check if your PR fulfills the following requirements:
Sample in sample app has been added / updated (for bug fixes / features)Icon has been created (if new sample) following the Thumbnail Style Guide and templatesNew major technical changes in the toolkit have or will be added to the Wiki e.g. build changes, source generators, testing infrastructure, sample creation changes, etc...Header has been added to all new source files (run build/UpdateHeaders.bat)Other information
It may be worthwhile to additionally expose the
Stepfield and the newly-addedDangerousGetReference/DangerousGetReferenceAtmethods. This would allow for an implementation ofReversethat avoids bounds-checking.